<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/meson.git/test cases/failing/2 missing file/test.json, branch cppmodules</title>
<subtitle>github.com: mesonbuild/meson.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/meson.git/'/>
<entry>
<title>Add expected stdout for failing-meson and warning-meson tests</title>
<updated>2020-04-30T19:41:35+00:00</updated>
<author>
<name>Jon Turney</name>
<email>jon.turney@dronecode.org.uk</email>
</author>
<published>2020-02-12T00:31:57+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/meson.git/commit/?id=3cff11a75b4af8824281b473bda1f8c45a4add7d'/>
<id>3cff11a75b4af8824281b473bda1f8c45a4add7d</id>
<content type='text'>
Initially produced using:

  for d in "test cases/failing/"* ; do rm -r _build ; ./meson.py setup "$d" _build | grep ERROR &gt;"$d"/expected_stdout.txt; done

then converted to json with jq using:

  jq --raw-input --slurp 'split("\n") | {stdout: map({line: select(. != "")})}' expected_stdout.txt &gt;test.json

or merged with existing json using:

  jq --slurp '.[0] + .[1]' test.json expected.json &gt;test.json.new

v2:
Add some comments to explain the match when it isn't totally obvious

v3:
Add or adjust existing re: in expected output to handle '/' or '\' path
separators appearing in message, not location.

v4:
Put expected stdout in test.json, rather than a separate expected_stdout.txt file
Park comments in an unused 'comments' key, as JSON doesn't have a syntax for comments
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Initially produced using:

  for d in "test cases/failing/"* ; do rm -r _build ; ./meson.py setup "$d" _build | grep ERROR &gt;"$d"/expected_stdout.txt; done

then converted to json with jq using:

  jq --raw-input --slurp 'split("\n") | {stdout: map({line: select(. != "")})}' expected_stdout.txt &gt;test.json

or merged with existing json using:

  jq --slurp '.[0] + .[1]' test.json expected.json &gt;test.json.new

v2:
Add some comments to explain the match when it isn't totally obvious

v3:
Add or adjust existing re: in expected output to handle '/' or '\' path
separators appearing in message, not location.

v4:
Put expected stdout in test.json, rather than a separate expected_stdout.txt file
Park comments in an unused 'comments' key, as JSON doesn't have a syntax for comments
</pre>
</div>
</content>
</entry>
</feed>
